Systems and Methods for Recording Resource Association for a Communications Environment

ABSTRACT

Included are embodiments for determining an extension-to-channel mapping. At least one embodiment includes determining, at a first time, a first extension-to-channel mapping configuration, the first extension-to-channel mapping configuration including an indication that at least one extension is coupled to a first recording channel. Similarly, some embodiments include determining, at a second time, a second extension-to-channel mapping configuration, the second extension-to-channel mapping configuration including an indication that the at least one extension is coupled to a second recording channel. Similarly, some embodiments include creating an extension-to-channel map, the extension-to-channel map indicating a configuration of the at least one extension, the first recording channel, and the second channel during a time period between the first time and the second time.

TECHNICAL FIELD

This application is related to mapping of channels in a recording environment.

BACKGROUND

In many communications environments, customers desire to record communications. As the number of communications devices in a communications environment may be very large, a large number of recorders and/or recorder channels may be utilized to facilitate recording of this data. More specifically, in some environments, a recorder may be utilized that includes a plurality of recording channels. As various communications devices may be coupled to the recorder via these channels, the recorder may be configured to record data associated with communications with devices on these extensions. As the number of devices (and/or extensions) coupled to the recorder increases, mapping of the extensions to the recorder channel may become difficult. With incorrect extension-to-channel mapping, location of recordings may become difficult.

SUMMARY

Included are embodiments for determining an extension-to-channel mapping. At least one embodiment includes determining, at a first time, a first extension-to-channel mapping configuration, the first extension-to-channel mapping configuration including an indication that at least one extension is coupled to a first recording channel. Similarly, some embodiments include determining, at a second time, a second extension-to-channel mapping configuration, the second extension-to-channel mapping configuration including an indication that the at least one extension is coupled to a second recording channel. Similarly, some embodiments include creating an extension-to-channel map, the extension-to-channel map indicating a configuration of the at least one extension, the first recording channel, and the second channel during a time period between the first time and the second time.

Also included are embodiments of a system for determining a trunk channel to recording channel association. At least one embodiment includes a first determining component configured to determine, at a first time, a first extension-to-channel mapping configuration, the first extension-to-channel mapping configuration including an indication that at least one extension is coupled to a first recording channel. Also included is a second determining component configured to determine, at a second time, a second extension-to-channel mapping configuration, the second extension-to-channel mapping configuration including an indication that the at least one extension is coupled to a second recording channel. Some embodiments include a mapping component configured to create an extension-to-channel map, the extension-to-channel map indicating a configuration of the at least one extension, the first recording channel, and the second channel during a time period between the first time and the second time.

Other systems, methods, features, and/or advantages of this disclosure will be or may become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description and be within the scope of the present disclosure.

BRIEF DESCRIPTION

Many aspects of the disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views. While several embodiments are described in connection with these drawings, there is no intent to limit the disclosure to the embodiment or embodiments disclosed herein. On the contrary, the intent is to cover all alternatives, modifications, and equivalents.

FIG. 1 is a diagram of an exemplary embodiment of a communications network illustrating a configuration for recording data and mapping extensions to channels.

FIG. 2 is a diagram of an exemplary embodiment of a communications network illustrating utilization of a replay component in mapping extensions to channels, similar to the diagram from FIG. 1.

FIG. 3 is a diagram of an exemplary embodiment of an Internet Protocol (IP) network illustrating a configuration for recording data and mapping extensions to recorders.

FIG. 4 is a diagram of an exemplary embodiment of a recorder, such as the recorder from FIGS. 1-3.

FIG. 5 is a diagram illustrating an exemplary embodiment of a plurality of recordings, such as recordings that may be captured in the networks from FIGS. 1-3.

FIG. 6 is a diagram of an exemplary embodiment of a cable component that may be utilized in the networks from FIGS. 1-3.

FIG. 7 is a diagram illustrating an exemplary embodiment of a graphical representation that may be utilized in determining an extension-to-channel mapping, such as in the networks from FIGS. 1-3.

FIG. 8 is a flowchart illustrating an exemplary embodiment of a process that may be utilized in mapping an extension to a channel, such as in the networks from FIGS. 1-3.

FIG. 9 is a flowchart illustrating an exemplary embodiment of a process that may be utilized in comparing recorded data in mapping an extension to a channel, similar the flowchart from FIG. 8.

FIG. 10 is a flowchart illustrating an exemplary embodiment of a process that may be utilized for capturing a code in mapping an extension to a channel, similar to the flowchart from FIG. 9.

FIG. 11 is a flowchart illustrating an exemplary embodiment of a process that may be utilized for mapping a change in an extension-to-channel configuration, similar to the flowchart from FIG. 10.

FIG. 12 is a flowchart illustrating an exemplary embodiment of a process that may be utilized in flagging a recording in response to a change in an extension-to-channel configuration.

FIG. 13 is a flowchart illustrating an exemplary embodiment of a process that may be utilized for using call detection in mapping an extension to a channel, similar to the flowchart from FIG. 12.

FIG. 14 is a flowchart illustrating an exemplary embodiment of a process that may be utilized in determining an extension-to-channel mapping, subsequent to a configuration change, similar to the flowchart from FIG. 13.

DETAILED DESCRIPTION

Included herein are embodiments that may be configured to facilitate mapping of extensions to channels and/or recorders. More specifically, in at least one exemplary embodiment, a recorder and/or other component may be configured to determine recording resource association (e.g., channel mapping) by sending a signal to an extension. Other embodiments may facilitate extension-to-channel association (and/or trunk channel-to-recording channel association and/or extension-to-recording resource association) by analyzing previously captured recording data to determine a current configuration.

Referring now to the drawings, FIG. 1 is a diagram of an exemplary embodiment of a communications network illustrating a configuration for recording data and mapping extensions to channels. As illustrated in the nonlimiting example of FIG. 1, communications devices 102 a, 102 b, and 102 c (which may include a telephone, an Internet Protocol telephone, a personal computer, a Personal Digital Assistant, a communications trunk, etc.) may be coupled to a call routing component 104 (which may include a switch, call controller, and/or other components). More specifically, the call routing component 104 may be configured to facilitate communications among communications devices 102 a, 102 b, and 102 c and/or with other communications devices. The call routing component may be configured to send substantive data (which may include voice data, screen data, etc.) and/or control data associated with the communication.

As communications devices 102 a, 102 b, and 102 c may be associated with a common network, these communications devices 102 may be associated with an extension. The extension may be a local extension in a local network, or may be a global extension in a Public Switched Telephone Network (PSTN), Internet Protocol (IP) environment, cellular environment, and/or other Wide Area Network (WAN) configuration. More specifically, in at least one nonlimiting example, communications device 102 a may be associated with the extension 1234. When a first user on a communications device (and/or other device) desires to contact a second user on the communications device 102 a, the first user can dial the extension 1234 to be placed in contact with the communications device 102 a.

Also included in the nonlimiting example of FIG. 1 is a recorder 106. The recorder 106 may be configured to record data communicated to and from communications devices 102. As illustrated in FIG. 1, the recorder 106 may be passively tapped to each of the lines between communications devices 102 a, 102 b, and 102 c and call routing component 104. More specifically, the communications device 102 a is coupled to channel 3 of the recorder 106. The communications device 102 b is coupled to channel 2 of the recorder 106. The communications device 102 c is coupled to channel 1 of the recorder 106.

As discussed above, as a plurality of extensions may be tapped for recording at the recorder 106, an accurate mapping of extensions to channels may become difficult. More specifically, in many current implementations, upon installation of the recorder 106, a technician may manually determine each extension to which the recorder channels are coupled. While this may become a tedious task for a technician, errors in this determination can cause loss of recorded data. Additionally, as maintenance and/or other changes to the network of FIG. 1 occur, the extensions may be moved and associated with different channels. As such, the mapping configuration that was previously determined may no longer be accurate. As such, in many current implementations, the technician may be forced to manually re-map the extension-to-channel connections.

While these current implementations utilize a manual mapping and re-mapping, embodiments of this disclosure may be configured for automatic mapping and/or re-mapping. More specifically, referring again to FIG. 1, the recorder 106 may include mapping logic (discussed in more detail below) for determining the extensions to which one or more of the channels of the recorder 106 are connected. Additionally, the recorder may utilize at least one of the recorder channels (CX, in this nonlimiting example) to facilitate utilization of the call routing component 104 in mapping and/or re-mapping an extension and channel.

As a nonlimiting example, the recorder may be configured to send a signal (via channel CX) to call one or more of the communications devices 102 to determine the channel to which these extensions are coupled. During operation of the communications devices 102 a, 102 b, and 102 c, the recorder 106 can determine that the communications device 102 a is currently not in use and/or has not been in use for a predetermined time period. Upon this determination, the recorder 106 can send a signal to the call routing component 104 to initiate a call to the communications device 102 a. The recorder 106 can then determine which channels recorded data (or were otherwise active) during the time that the recorder 106 facilitated the call to the communications device 102 a. If the recorder 106 determines that only one channel was active during this time, the recorder 106 can determine the channel to which the extension 1234 is coupled (in this nonlimiting example C1). If more than one channel was active during this time, additional calls may be facilitated by the recorder 106 to the communications device 102 a. By analyzing data on the various calls, the recorder 106 can determine that the channels C1, C2, C3, in this nonlimiting example, are coupled to extensions 1234, 5000, and 7456, respectively.

Similarly, some embodiments may be configured such that the recorder 106 is configured to facilitate a call to an extension, such as extension 5000. Again, depending on the particular configuration, the recorder 106 can initiate the call and/or the call routing component 104 can initiate the call. Regardless, upon connecting with the communications device 102 b at extension 5000, the recorder 106 can facilitate sending data to the communications device 102 b. By sending data to the communications device 102 b, the recorder 106 can record the sent data and store the sent data at a data storage component (not shown) or elsewhere). The recorder 106 can then compare the data sent with data received at the recorder 106. As the recorder 106 may be recording data from a plurality of extensions, the recorder 106 can compare the recorded data with the sent data until a match is found. Upon finding a match, the recorder 106 can map the extension from where the recording was received to the channel that captured the data.

One should note that a map, as disclosed herein may include a visual map and/or a non-visual map. Additionally, depending on the particular embodiment, the map may be stored at a recorder, at a call routing component, at a data storage component and/or elsewhere on the network. Additionally, when accessing a created map, a lookup table may be utilized to locate the desired data.

Similarly, some embodiments may be configured to facilitate the dialing of an extension and, upon connection with the communications device 102 at that extension, dialing a predetermined code for identifying the channel to which that extension is coupled. As a nonlimiting example, upon connecting with extension 7456, the recorder 106 can send the following code [55*7456*55]. This exemplary code may be utilized to indicate the beginning of the code, the extension number being dialed, and the end of the code. More specifically, [55*] may be a code that indicates that the recorder 106 is determining an extension-to-channel mapping. Additionally, [7456] may be utilized to indicate the extension that is dialed. Finally, in this nonlimiting example, [*55] may be used to indicate that the code is finished.

Thus, in operation, the recorder 106 can facilitate a communications session with the communications device 106 c. Upon establishment of the communications session, the recorder can facilitate (via channel CX, for example) sending of the code [55*7456*55] to the communications device 106 c. Because the recorder 106 is coupled to the communications path to the communications device 106 c, the recorder 106 receives and records the code that was sent. The recorder 106 can then recognize that a mapping test is being performed by recognizing that the recorded code includes a sub-code of [55*]. The recorder 106 can then determine that the extension at this particular channel by determining that the sub-code [7456] was recorded after the sub-code [55*]. The recorder 106 can then determine that no other data is forthcoming in this code from the sub-code [*55]. From this information, the recorder 106 can determine the channel that is connected to that particular extension.

One should note that while in the description above, a particular code was sent to the extension, this code is a nonlimiting example, as any code may be utilized for determining the channel to which an extension is connected. Additionally, while the above nonlimiting examples discuss dialing information to determine an extension-to-channel mapping, some embodiments may be configured such that the recorder 106 can facilitate the playing and recording of sounds. The recorder 106 can then use recognition logic to match the sent sounds to the recorded sounds.

Additionally, while the nonlimiting examples described above illustrate a configuration where the recorder 106 is configured to facilitate initiation of a communication for mapping extensions to channels, this is not a requirement. More specifically, in at least one exemplary embodiment, the recorder 106 may be configured for automatic call detection to monitor communications and recordings of the communications devices 102. Data associated with the communications and recordings may be stored and used to determine an extension-to-channel mapping. More specifically, the recorder 106 may monitor start times for various communications and start times for various recordings. By comparing this data, the recorder 106 may be able to determine a probability associated with an extension-to-channel mapping. If the probability that a particular channel is coupled to a particular extension reaches a predetermined threshold, the recorder 106 can map this configuration.

While the above exemplary embodiment discloses using start times to determine an extension-to-channel mapping, this is also a nonlimiting example. More specifically, other data, such as call and recording duration, data communicated versus data recorded, end times of a communication and recording, as well as other data.

Additionally, one should note that in at least one exemplary embodiment, one or more of the communications devices 102 may be configured to send screen data to the recorder 106. The recorder 106 (and/or other component) may be configured to interpret one or more characteristics of the recorded screen data to determine the current mapping configuration.

FIG. 2 is a diagram of an exemplary embodiment of a communications network illustrating utilization of a replay component in mapping extensions to channels, similar to the diagram from FIG. 1. As illustrated in the nonlimiting example of FIG. 2, communications devices 202 a, 202 b, and 202 c are coupled to the call routing component 204, as discussed above. Additionally, a recorder 206 may be coupled to a line between the call routing component 104 and the communications devices 202 at a plurality of channels (C1, C2, and C3). As also illustrated, a communications device 210 may facilitate a communications session with any of the communications devices 202, via a network 200. The network 200 can include a PSTN, an IP network, a cellular network and/or other networks. Additionally, while illustrated as being separate from the network 200, the call routing component 204 may be, depending on the particular configuration, included with the network 200.

Also included in the nonlimiting example of FIG. 2 is a replay component 208. In this particular configuration, the replay component 208 may be configured to facilitate a determination of the channel and extension mapping. More specifically, the replay component 208 may be configured, in at least one embodiment, to initiate at least one communications request to the communications devices 202. The replay component 208 may also be configured to retrieve recording data from the recorder 206 (or at a data storage component, not shown) for determining the extension-to-channel mapping. More specifically, similar to embodiments discussed above, the replay component 208 may be configured to facilitate initiation of a communication, monitoring of all (or at least a portion) communications that are received at the recorder 208, and determine from the monitoring the channel that is associated with the dialed extension.

Similarly, in some embodiments, the replay component 208 may be configured to dial an extension to establish a communications session. When a communications session is established, the replay component 208 can send a signal for recording at the recorder 206. Once recorded, the replay component 208 can access the plurality of recordings captured by the recorder 206. As the recordings may be stored according to the channel from which they were received, the replay component 208 can compare the sent signal with the recorded data and determine the channel that corresponds with the extension that was dialed.

Also similar to embodiments discussed above, the replay component 208 may be configured to dial a predetermined code to determine an extension-to-channel mapping. More specifically, in at least one exemplary embodiment, upon establishing a communications session with a desired extension, the replay component may send the predetermined code to the extension, for recording by the recorder 206. Upon recording the data, the recorder may determine that the recorded data is associated with a channel mapping and send the channel and/or extension to the replay component 208. From this data, the replay component 208 may determine the extension-to-channel mapping.

One should note that while the exemplary embodiments discussed above include configurations where each extension is mapped to one channel, this is a nonlimiting example. More specifically, in at least one embodiment, an extension may be coupled to a plurality of channels and/or recorded by a plurality of recorders. In such a scenario, the at least one recorder 106, 206 may be configured to determine the extensions that are coupled to more than one channel. Additionally, in configurations where the plurality of channels span a plurality of recorders 106, 206, at least one of the recorders 106, 206 (and/or other components) may be configured to provide a mapping that includes this information. Similarly, in at least one exemplary embodiment, a plurality of extensions may be mapped to a single recorder and/or recorder channel.

FIG. 3 is a diagram of an exemplary embodiment of an Internet Protocol (IP) network illustrating a configuration for recording data and mapping extensions to recorders. As illustrated in the nonlimiting example of FIG. 3, communications devices 302 a, 302 b, and 302 c may be coupled to a call routing component 304, which may be coupled to a network 300 and a communications device 310. While in the previous nonlimiting examples, a single recorder 106, 206 included a plurality of channels for recording a plurality of extensions, in this nonlimiting example, a plurality of recorders may be included to record a plurality 306 of lines.

More specifically, the recorder 306 a may be coupled to an extension associated with the communications device 302 c (e.g., 7456). The recorder 306 b may be coupled to an extension associated with the communications device 102 b (e.g., 5000). The recorders 306 c, 306 d, and 306 e may be coupled, via a load balancer 312 to an extension associated with the communications device 102 a (e.g., 1234).

In the exemplary embodiment of FIG. 3, one or more of the recorders 306 may be configured to facilitate an extension-to-channel mapping, as discussed above. Additionally, some embodiments may be configured such that one recorder 306 may be configured to perform one technique of extension-to-channel mapping and another recorder 306 may be configured to perform a different technique for extension to recorder mapping. Additionally, depending on the particular configuration, a recorder 306 and/or other component may be configured to store the determined extension-to-channel mapping.

One should note that while the IP network from FIG. 3 illustrates a configuration where one or more of the recorders are configured to determine an extension-to-channel (and/recorder) mapping, this is a nonlimiting example, as another component (e.g., the load balancer 312, the call routing component 104, and/or other component not shown) may be configured to facilitate this mapping.

One should note that while the call routing component 304 is illustrated as a single component, the call routing component 304 may, depending on the particular configuration, represent a Service Switching Point (SSP), a Signal Transfer Point (STP), a call control server, and/or other components that facilitate a communications session.

One should also note that in addition to voice and control data, embodiments disclosed herein may be configured to record and/or utilize screen capture data to determine an extension-to-channel mapping. In at least one nonlimiting example, a recorder may be configured to determine whether the recorder can record screen capture data. Additionally, the call routing component 304 (and/or other network component) may be configured to create a list of recorders in the network that are capable of recording screen capture data. This information may be used to determine whether a communication is being received at a particular recorder.

FIG. 4 is a diagram of an exemplary embodiment of a recorder, such as a recorder from FIGS. 1-3. Although a wire-line recorder 106, 206, 306 is illustrated, this discussion can be applied to wireless devices, as well. Generally, in terms of hardware architecture, as shown in FIG. 4, the recorder 106, 206, 306 may include a processor 482, a memory component 484 (which may include volatile and/or nonvolatile memory components), a display interface 494, a data storage component 495, one or more input and/or output (I/O) device interface(s) 496, and/or one or more network interface 498 that are communicatively coupled via a local interface 492. The local interface 492 can include, for example but not limited to, one or more buses or other wired or wireless connections. The local interface 492 may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers to enable communications. Further, the local interface may include address, control, and/or data connections to enable appropriate communications among the aforementioned components. The processor 482 may be a device for executing software, particularly software stored in the memory component 484.

The processor 482 can be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the recorder 106, a semiconductor based microprocessor (in the form of a microchip or chip set), a macroprocessor, or generally any device for executing software instructions.

The memory component 484 can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and/or nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.). Moreover, the memory component 484 may incorporate electronic, magnetic, optical, and/or other types of storage media. One should note that some embodiments of the memory component 484 can have a distributed architecture (where various components are situated remotely from one another), but can be accessed by the processor 482.

The software in memory component 484 may include one or more separate programs, each of which includes an ordered listing of executable instructions for implementing logical functions. In the example of FIG. 4, the software in the memory component 484 may include an operating system 486, mapping logic 487, and recording logic 488. The operating system 486 may be configured to control the execution of other computer programs and provides scheduling, input-output control, file and data management, memory management, and communication control and related services.

A system component and/or module embodied as software may also be construed as a source program, executable program (object code), script, or any other entity comprising a set of instructions to be performed. When constructed as a source program, the program is translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the memory component 484, so as to operate properly in connection with the operating system 486.

The Input/Output devices that may be coupled to system I/O Interface(s) 496 may include input devices, for example but not limited to, a keyboard, mouse, scanner, microphone, etc. Further, the Input/Output devices may also include output devices, for example but not limited to, a printer, display, speaker, etc. Finally, the Input/Output devices may further include devices that communicate both as inputs and outputs, for instance but not limited to, a modulator/demodulator (modem; for accessing another device, system, or network), a radio frequency (RF) or other transceiver, a telephonic interface, a media duplication system, a router, etc.

Additionally included are one or more network interfaces 498 for facilitating communication with one or more other devices. More specifically, a network interface 498 may include any component configured to facilitate a connection with another device. While in some embodiments, among others, the recorder 106, 206, 306 can include a network interface 498 that includes a Personal Computer Memory Card International Association (PCMCIA) card (also abbreviated as “PC card”) for receiving a wireless network card, however this is a nonlimiting example. Other configurations can include the communications hardware within the computing device, such that a wireless network card is unnecessary for communicating wirelessly. Similarly, other embodiments include network interfaces 498 for communicating via a wired connection. Such interfaces may be configured with Universal Serial Bus (USB) interfaces, serial ports, and/or other interfaces.

Additionally included are one or more channels C1, C2, C3, C4, and CX, which may be configured to facilitate recording of a communication. While the channels C1, C2, C3, C4, and CX may be coupled via the system I/O interface(s) 496 and/or the network interface(s) 498, this is not a requirement.

If recorder 106, 206, 306 includes a personal computer, workstation, or the like, the software in the memory component 484 may further include a basic input output system (BIOS) (omitted for simplicity). The BIOS is a set of software routines that initialize and test hardware at startup, start the operating system 486, and support the transfer of data among the hardware devices. The BIOS is stored in ROM so that the BIOS can be executed when the recorder 106, 206, 306 is activated.

When recorder 106, 206, 306 is in operation, the processor 482 may be configured to execute software stored within the memory component 484, to communicate data to and from the memory component 484, and to generally control operations of the recorder 106, 206, 306 pursuant to the software. Software in memory, in whole or in part, may be read by the processor 482, perhaps buffered within the processor 482, and then executed.

One should note that while the description with respect to FIG. 4 includes a recorder controller as a single component, this is a nonlimiting example. More specifically, in at least one embodiment, the recorder 106, 206, 306 can include a plurality of servers, personal computers, and/or other devices. Similarly, while the routing logic 487, the recording logic 488 and the presence logic 499 are each illustrated in FIG. 4 as single software components, this is also a nonlimiting example. In at least one embodiment, the presence logic 499 may include one or more components, embodied in software, hardware, and/or firmware. Similarly, routing logic and/or the recording logic 488 may include one or more logical components. Additionally, while the routing logic 487, the presence logic 499, and the recording logic 488 are depicted as residing on a single computing device, such as the recorder 106, 206, 306 may include one or more devices, the presence logic 499 may include one or more components residing on one or more different devices.

Similarly, while the discussion with regard to FIG. 4 refers to a recorder 106, 206, 306, the above description may be applied to other components discussed herein. More specifically, a call routing device 104, 204, 304, a communications device 102, 202, 302, a load balancer 312, a replay component 208, a recorder controller (not shown), a call control server (not shown), and/or other components may include similar elements and/or operate similarly.

FIG. 5 is a diagram illustrating an exemplary embodiment of a plurality of recordings, such as recordings that may be captured in the networks from FIGS. 1-3. As illustrated in the nonlimiting example of FIG. 5, a recorder 106, 206, 306 (referred to hereinafter as recorder 106) may be configured to record data from one or more communications sessions for an extension, the data recordings represented as recordings 516 a-516 j. Additionally illustrated in this nonlimiting example, an extension-to-channel mapping has been performed at vertical line 518 a. During this mapping, the recorder 106, replay component 208, and/or other components may determine that this extension is currently sending recording data to channel 1 (C1). The recorder 106 may receive recordings 516 a, 516 b, and 516 d before performing another mapping. At vertical line 518 b, a mapping was performed and, again, it was determined that this extensions sends recording data to C1. The recorder 106 may then receive recordings 516 d, 516 e, and 516 f before another mapping occurs. At vertical line 518 c a mapping was performed that indicates that this extension is now sending data to C44. The recorder 106 may then receive recordings 516 g, 516 f, and 516 j before another mapping is performed. At vertical line 518 d, the mapping determined that this extension is sending data to C44.

While a determination can be made that the recordings 516 a, 516 b, and 516 c were received a C1 and that recordings 516 g, 516 h, and 516 j were received at C44, there may be some confusion regarding recordings 516 d, 516 e, and 516 f. More specifically, while a determination may be made that these recordings were either received at C1 or C44, but depending on the particular configuration, a definitive determination may be unreachable as to exactly when the channel change occurred. In such a scenario, the mapping logic 487 may be configured to flag these recordings as being mapped to C1 or C44. Similarly, the mapping logic 487 may be configured to determine the appropriate mapping for these recordings using a different mapping technique, such as described above.

FIG. 6 is a diagram of an exemplary embodiment of a cable component that may be utilized in the networks from FIGS. 1-3. As illustrated in the nonlimiting example of FIG. 6, a cable component 620 may be included with the call routing component 104, 204, 304 (referred to hereinafter as routing component 104). More specifically, the cable component 620 may be configured as an intermediary between a recorder 106 and an extension. Additionally, channels may be sequentially configured on the ports of the cable component 620. As shown in the nonlimiting example of FIG. 6, C1 is coupled to port 9 and is thus coupled to extension 1234, C2 is coupled to port 11 and is thus coupled to extension 5000, etc. Thus, upon a determination of one extension-to-channel mapping, the other channels of a recorder may be determined.

FIG. 7 is a diagram illustrating an exemplary embodiment of a graphical representation that may be utilized in determining an extension-to-channel mapping, such as in the networks from FIGS. 1-3. As illustrated in the nonlimiting example of FIG. 7, an extension may be determined via automatic call detection, as described above. More specifically, a plurality of calls and recordings may be monitored to determine start time, end time, duration, midpoint, data communicated, etc. A comparison of the recorded data with the communication data may provide various probabilities related to the channels of a recorder 106. Additionally, the recording logic 487 may be configured to compare the probabilities against a predetermined threshold. If a channel exceeds the threshold, that channel may be mapped to the extension.

Referring to graph 772, channels C1-C4 (724 a-724 d) and C6-C10 (724 f-724 j) have been determined to have various probabilities for being coupled to this extension. Additionally, C5 726 has been determined to have a much higher probability of being coupled to this extension. As C5 726 exceeds the threshold 728, the recording logic 487 may determine that C5 is coupled to this extension, and map accordingly.

One should note that while the configuration of FIG. 7 may be determined based on the probability a channel is coupled to an extension, this is a nonlimiting example. More specifically, in at least one embodiment, the mapping logic 487 may be configured to use a process of elimination (determining which channels are not coupled to an extension) to conclude which channel is coupled to an extension. More specifically, in at least one exemplary embodiment, if the mapping logic 487 determines that at 12:00 on Jan. 1, 2007 no call was recorded from extension 1234 at channel C7, the mapping logic 478 can determine that C7 is not coupled to extension 1234. Similar data may be used to eliminate other channels and determine the appropriate mapping.

One should also note that while a threshold 726 of approximately 85% is illustrated in FIG. 7, this is also a nonlimiting example. More specifically, depending on the particular configuration, a user or other entity may determine an acceptable threshold 726. Similarly, in some embodiments, a threshold may be automatically set, based on the particular environment.

FIG. 8 is a flowchart illustrating an exemplary embodiment of a process that may be utilized in mapping an extension to a channel, such as in the networks from FIGS. 1-3. As illustrated in the nonlimiting example of FIG. 8, the mapping logic 487 may initiate a call to an extension (block 832). The mapping logic 487 can determine the channels that are in use during the call (block 834). The mapping logic 487 can compare the determined channels with previously compiled data (block 836). As discussed above, the mapping logic 487 may be configured to make one or more calls and compare data associated with the time that the one or more calls were made. From this, the mapping logic 487 can determine the extension-to-channel mapping. A determination can then be made as to whether the channel mapping has been determined (block 838). If so, the process may end. If no channel mapping has been determined, the flowchart may return to block 832.

FIG. 9 is a flowchart illustrating an exemplary embodiment of a process that may be utilized in comparing recorded data in mapping an extension to a channel, similar the flowchart from FIG. 8. As illustrated in the nonlimiting example of FIG. 9, the mapping logic 487 can initiate a call to an extension (block 932). The call may then be answered (block 934). One should note that the answering of the call may be initiated by the communications device 102 that is coupled to that extension and/or facilitated by a switch or other call routing component 104. The mapping logic 487 can send data to the extension for recording (block 936). The data can include tones or other sounds, embedded data, etc. The mapping logic can then compare the recorded data with the sent data to determine the channel (block 938).

More specifically, in at least one exemplary embodiment, the mapping logic can compare all data recorded by the recorder 106. Similarly, some embodiments can utilize characteristics associated with the sent data to more quickly determine the current mapping. The characteristics may include a time that data was sent, a size of data, and/or other characteristics.

FIG. 10 is a flowchart illustrating an exemplary embodiment of a process that may be utilized for capturing a code in mapping an extension to a channel, similar to the flowchart from FIG. 9. As illustrated in the nonlimiting example of FIG. 10, the mapping logic 487 can initiate a call to an extension (block 1032). The call may then be answered (block 1034). The mapping logic 487 may send a code that includes the extension dialed (block 1036). As discussed above, the mapping logic 487 may send a code that is recognizable by the recording logic 488 as a mapping code. The recording logic 488 can capture the code, determine the extension from the code, and send the extension number from a channel that recorded the data to the mapping logic 487 (block 1038).

FIG. 11 is a flowchart illustrating an exemplary embodiment of a process that may be utilized for mapping a change in an extension-to-channel configuration, similar to the flowchart from FIG. 10. As illustrated in the nonlimiting example of FIG. 11, the mapping logic 487 maps channels and/or recorders to extensions (block 1132). The mapping logic 487 can then start a timer (block 1134). The timer can expire (block 1136). Upon expiration of the timer, the mapping logic 487 can initiate re-mapping (block 1138). More specifically, as discussed above, the mapping logic 487 may be configured to map (and re-map) the extensions to channels on a periodic basis, on an aperiodic basis, on a continuous basis, at a user request, etc. One should note that while the description with regard to FIG. 11 refers to periodic re-mapping, this is a nonlimiting example.

After initiating re-mapping, the mapping logic can determine whether there has been a change in the current extension-to-channel map (block 1140). If there has not been a change in the mapping, the flowchart can return to setting the timer, at block 1134. If, on the other hand, a change is detected at block 1140, the mapping logic 487 can determine the type of change (block 1142). If the change includes a determination that a channel is no longer coupled to an extension (or vice versa), the mapping logic 487 can map the new channel (block 1144). The mapping logic 487 can keep the old mapping of this channel (and/or extension) for a predetermined number of re-maps or until a replacement is detected (block 1146).

More specifically, if the mapping logic 487 determines that a channel is no longer coupled to an extension, the mapping logic 487 (in at least one embodiment) may determine that a connection is loose or inadvertently lost and/or other temporary condition that will be resolved. As such, the mapping logic 487 may keep the previously determined map for this channel and/or extension for a predetermined time, predetermine number of re-maps, and/or for another duration.

If, at block 1142, the mapping logic 487 determines that there is a replacement change (e.g., a new extension is coupled to a channel, which replaces the previously determined extension), the mapping logic 487 can replace the old mapping with the new mapping. The mapping logic 487 can determine whether the process is ending (block 1148), and if not, the flowchart returns to block 1134 to start the timer.

FIG. 12 is a flowchart illustrating an exemplary embodiment of a process that may be utilized in flagging a recording in response to a change in an extension-to-channel configuration. As illustrated in the nonlimiting example of FIG. 12, the mapping logic 487 can map a channel (block 1232). The recording logic 488 can record data (block 1234). The mapping logic can then tag and store the recorded data according to the mapping (block 1236). More specifically, in at least one exemplary embodiment, upon determining a mapping, a recorder can record a communication at a channel. In addition to capturing data from the communication, the recording logic 488 (or mapping logic 487) can flag the recording with the appropriate extension. If the communication is an internal communication, the communication may be flagged with both (or all) extensions associated with the communication. The recording can then be stored according to the flagging.

One should note that in at least one exemplary embodiment, the recording may be stored as an audio file (e.g., .wav file, .mp3 file, etc.) and a description file (e.g., .xml file, .txt file, etc.) may be included with the audio file. The description file may include the extension and/or channel information. Similarly, some embodiments may include storing the recording (which may include the audio file and/or the description file) in a folder corresponding to the extension and/or channel from where the communication was received.

Referring back to FIG. 12, the mapping logic 487 can re-map the channel (block 1238). As discussed above, re-mapping can occur at any number of times. The mapping logic 487 can then determine whether there is a mapping change (block 1240). If there is not a mapping change, the mapping logic 487 can determine whether the process is ending (block 1242). If a change is detected, the mapping logic 487 can determine the nature of the change (block 1242). The mapping logic can flag recordings between mapping and re-mapping as unsure but provide possible channels (block 1244). More specifically, as discussed above, in at least one exemplary embodiment, if a change in the mappings occur, the mapping logic 487 may have uncertainty as to exactly when the change occurred and, thus, may have uncertainty regarding the source of one or more recordings. As such, the mapping logic 487 may be configured to flag one or more of these recordings with an uncertain flag, but indicate that the mapping may have originated from an extension in accordance with the previous map or with an extension in accordance with the new map. Other embodiments are also discussed to determine the source of these recordings. The mapping logic 487 can then determine whether the process can end (block 1242).

FIG. 13 is a flowchart illustrating an exemplary embodiment of a process that may be utilized for using call detection in mapping an extension to a channel, similar to the flowchart from FIG. 12. As illustrated in the nonlimiting example of FIG. 13, the mapping logic 487 can collect data from recordings (block 1332). The mapping logic 487 can utilize collected data to determine a probability of a channel corresponding to an extension (block 1334). For the next channel, the mapping logic 487 can determine an extension that exceeds a predetermined probability threshold (block 1336). The mapping logic 487 can then map the channel to that extension (block 1338). A determination can be made whether the process can end (block 1340).

FIG. 14 is a flowchart illustrating an exemplary embodiment of a process that may be utilized in determining an extension-to-channel mapping, subsequent to a configuration change, similar to the flowchart from FIG. 13. As illustrated in the nonlimiting example of FIG. 14, the mapping logic 487 can map a channel (block 1432). The recording logic 488 can record data associated with a communication (block 1434). The mapping logic 487 can tag and/or store recorded data according to the mapping (block 1436). The mapping logic 487 can then re-map the channel (block 1438). The mapping logic 487 can then determine a mapping change (block 1440). If there is not mapping change, the process can proceed to block 1440. If, on the other hand, there is a mapping change, the mapping logic 487 can determine the nature of the change (block 1442). The mapping logic can then utilized collected recording data to determine a channel for the extension during the transition (block 1438). The mapping logic can then determine whether the process can end (block 1440). If not, the process can return to recording data (block 1434).

As discussed above, when a mapping change occurs, there may be uncertainty with regard to recordings that were received between the time of a previous mapping and the mapping change. As such, in at least one embodiment, the mapping logic 487 may be configured to utilize a plurality of mapping techniques for determining mapping for the uncertain recordings. While FIG. 14 illustrates utilization of the automatic call detection, described above, to determine mapping for the uncertain recordings, it will be appreciated that other techniques may also be utilized. As a nonlimiting example, in at least one exemplary embodiment, when a change occurs, a mapping algorithm may be utilized to work back in time to identify when the calls no longer match Computer Telephone Integration (CTI) data and deduct that this is when the change occurred. Other configurations may also be utilized.

It should be noted that a customer center may include, but is not limited to, outsourced contact centers, outsourced customer relationship management, customer relationship management, voice of the customer, customer interaction, contact center, multi-media contact center, remote office, distributed enterprise, work-at-home agents, remote agents, branch office, back office, performance optimization, workforce optimization, hosted contact centers, and speech analytics, for example.

Additionally included in this disclosure are embodiments of integrated workforce optimization platforms, as discussed in U.S. application Ser. No. 11/359,356, filed on Feb. 22, 2006, entitled “Systems and Methods for Workforce Optimization,” which is hereby incorporated by reference in its entirety. At least one embodiment of an integrated workforce optimization platform integrates: (1) Quality Monitoring/Call Recording—voice of the customer; the complete customer experience across multimedia touch points; (2) Workforce Management—strategic forecasting and scheduling that drives efficiency and adherence, aids in planning, and helps facilitate optimum staffing and service levels; (3) Performance Management—key performance indicators (KPIs) and scorecards that analyze and help identify synergies, opportunities and improvement areas; (4) e-Learning—training, new information and protocol disseminated to staff, leveraging best practice customer interactions and delivering learning to support development; and/or (5) Analytics—deliver insights from customer interactions to drive business performance. By way of example, the integrated workforce optimization process and system can include planning and establishing goals—from both an enterprise and center perspective—to ensure alignment and objectives that complement and support one another. Such planning may be complemented with forecasting and scheduling of the workforce to ensure optimum service levels. Recording and measuring performance may also be utilized, leveraging quality monitoring/call recording to assess service quality and the customer experience.

The embodiments disclosed herein can be implemented in hardware, software, firmware, or a combination thereof. At least one embodiment, disclosed herein is implemented in software and/or firmware that is stored in a memory and that is executed by a suitable instruction execution system. If implemented in hardware, as in an alternative embodiment embodiments disclosed herein can be implemented with any or a combination of the following technologies: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, a programmable gate array(s) (PGA), a field programmable gate array (FPGA), etc.

One should note that the flowcharts included herein show the architecture, functionality, and operation of a possible implementation of software. In this regard, each block can be interpreted to represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order and/or not at all. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

One should note that any of the programs listed herein, which can include an ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “computer-readable medium” can be any means that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (a nonexhaustive list) of the computer-readable medium could include an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical). In addition, the scope of the certain embodiments of this disclosure can include embodying the functionality described in logic embodied in hardware or software-configured mediums.

One should also note that conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more particular embodiments or that one or more particular embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.

It should be emphasized that the above-described embodiments are merely possible examples of implementations, merely set forth for a clear understanding of the principles of this disclosure. Many variations and modifications may be made to the above-described embodiment(s) without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure. 

1. A method for determining an extension-to-channel association, comprising: determining, at a first time, a first extension-to-channel association configuration, the first extension-to-channel association configuration including an indication that at least one extension is coupled to a first recording channel; determining, at a second time, a second extension-to-channel association configuration, the second extension-to-channel association configuration including an indication that the at least one extension is coupled to a second recording channel; and determining a change in the first extension to channel association configuration.
 2. The method of claim 1, further comprising creating an extension-to-channel mapping, the extension-to-channel mapping indicating a configuration of the at least one extension, the first recording channel, and the second channel during a time period between the first time and the second time.
 3. The method of claim 2, wherein the map includes at least one of the following: a visual map stored at a recorder, a non-visual map stored at a recorder, a visual map stored at a server, and a non-visual map stored at a server.
 4. The method of claim 1, wherein the extension-to-channel association indicates that the at least one channel is coupled to either the first recording channel or the second recording channel, during the time period between the first time and the second time.
 5. The method of claim 1, further comprising determining, from previously stored data, a first probability that the at least one extension is coupled to the first recording channel during the time period between the first time and the second time.
 6. The method of claim 5, further comprising determining, from previously stored data, a second probability that the at least one extension is coupled to the second recording channel during the time period between the first time and the second time.
 7. The method of claim 5, further comprising determining whether the first probability exceeds a predetermined threshold.
 8. The method of claim 1, further comprising recording data received from the at least one extension.
 9. The method of claim 1, further comprising, in response to a determination that the first extension-to-channel association configuration is the same as the second extension-to-channel mapping configuration, utilizing the first extension-to-channel mapping configuration for the extension-to-channel map.
 10. A system for determining a trunk channel to recording channel association, comprising: a first determining component configured to determine, at a first time, a first extension-to-channel mapping configuration, the first extension-to-channel mapping configuration including an indication that at least one extension is coupled to a first recording channel; a second determining component configured to determine, at a second time, a second extension-to-channel mapping configuration, the second extension-to-channel mapping configuration including an indication that the at least one extension is coupled to a second recording channel; and a mapping component configured to create an extension-to-channel map, the extension-to-channel map indicating a configuration of the at least one extension, the first recording channel, and the second channel during a time period between the first time and the second time.
 11. The system of claim 10, wherein the extension-to-channel map indicates that the at least one channel is coupled either the first recording channel or the second recording channel, during the time period between the first time and the second time.
 12. The system of claim 10, further comprising a third determining component configured to determine, from previously stored data, a first probability that the at least one extension is coupled to the first recording channel during the time period between the first time and the second time.
 13. The system of claim 12, further comprising a fourth determining component configured to determine, from previously stored data, a second probability that the at least one extension is coupled to the second recording channel during the time period between the first time and the second time.
 14. The system of claim 12, further comprising a fifth determining component configured to determine whether the first probability exceeds a predetermined threshold.
 15. The system of claim 10, further comprising a recording component configured to record data received from the at least one extension.
 16. The system of claim 10, further comprising a utilizing component configured to utilize, in response to a determination that the first extension-to-channel mapping configuration is the same as the second extension-to-channel mapping configuration, the first extension-to-channel mapping configuration for the extension-to-channel map.
 17. A system for determining an extension-to-recording resource association, comprising: a first determining component configured to determine, at a first time, a first extension-to-channel mapping configuration, the first extension-to-channel mapping configuration including an indication that at least one extension is coupled to a first recording channel; a second determining component configured to determine, at a second time, a second extension-to-channel mapping configuration, the second extension-to-channel mapping configuration including an indication that the at least one extension is coupled to a second recording channel; a mapping component configured to create an extension-to-channel map, the extension-to-channel map indicating a configuration of the at least one extension, the first recording channel, and the second channel during a time period between the first time and the second time; and a recording component configured to record data received from the at least one extension.
 18. The system of claim 17, wherein the extension-to-channel map indicates that the at least one channel is coupled to either the first recording or the second recording channel, during the time period between the first time and the second time.
 19. The system of claim 17, further comprising a third determining component configured to determine, from previously stored data, a first probability that the at least one extension is coupled to the first recording channel during the time period between the first time and the second time.
 20. The system of claim 19, further comprising a fourth determining component configured to determine, from previously stored data, a second probability that the at least one extension is coupled to the second recording channel during the time period between the first time and the second time.
 21. The system of claim 19, further comprising means for determining whether the first probability exceeds a predetermined threshold.
 22. The system of claim 17, further comprising a utilizing component configured to utilize, in response to a determination that the first extension-to-channel mapping configuration is the same as the second extension-to-channel mapping configuration, the first extension-to-channel mapping configuration for the extension-to-channel map. 